[FIX] CAS does not share secrets when operating multiple server instances #8654
+35
−20
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@RocketChat/core
Closes #8032
This fixes CAS login when running multiple instances of RocketChat. When using CAS, a so called credentialsToken is stored in the server process to identify login attempts via CAS pop-up. This is bad when it comes to running several instances of RocketChat because it can not be guaranteed to hit the same instance again. Thus, I changed storing those tokens in MongoDB. In addition, I added a cleanup mechanism to delete outdated tokens of failed login attempts.